dl-breadcrumbs__homedl-breadcrumb-item__separatorConfiguration and programmingdl-breadcrumb-item__separatorProgramming with CODESYSdl-breadcrumb-item__separatorAutomation Builderdl-breadcrumb-item__separator...dl-breadcrumb-item__separatorProgramming of Applications dl-breadcrumb-item__separatorRuntime systems, OPC UA serverdl-breadcrumb-item__separatorData Link with Data Sources dl-breadcrumb-item__separatorCODESYS Symbolic data source type
dl-pagination__prev-inactivedl-pagination__prev-activedl-pagination__next-inactivedl-pagination__next-active
CODESYS Symbolic data source type dl-permalink__symbolPermalink

The CODESYS Symbolic data source type is available only together with a CODESYS device. However, then it is advantageous to use this type.

Below a CODESYS HMI device, you can configure the data link either with the CODESYS Symbolic data source type or CODESYS ApplikationV3 data source type. We recommend that you select CODESYS ApplikationV3 as the data source type only when there are no resources for the symbol configuration available on the remote device. For example, this is the case with embedded or mini PLCs whose applications often do not contain a symbol configuration.

The requirement for a connection setup is that symbols have been configured in the remote device and as a result a symbol file exists. The application in the remote device has a symbol configuration. Then the data link can be established via symbolic monitoring.

In the case of symbolic monitoring, the symbol file on the remote device is read and the stored variable information is used for the data source variables and the data transfer. The advantage is that the application does not have to be updated in the local device when someone modifies the remote application without updating its symbol configuration. If the symbol file is also located on your development system (either a file or a symbol configuration object as part of your project), then the local symbol file can also be read. Then you can work offline during the development phase.

During the development phase, you can create a variable list offline by means of local symbol configuration files. In this way, you can develop a local application offline based on the symbol information without a connection to a data source.

As of CODESYS Communication 4.5.0.0 and programming system / runtime system V3.5 SP20, structured data types are transferred with their original type name instead of the previously used name ‎GeneratedType_<number>‎.

The following connection types are possible:

  • “ CODESYS V2”

    The devices exist in the same network. The V2 runtime on the remote PLC provides a communication interface.

  • “ CODESYS V2 (via gateway)”

    The devices do not exist in the same network. They are connected via a V2 gateway.

    Note: For this connection, a “ CODESYS V2.3 Gateway Server Gateway Server” (V2 gateway) has to be installed on the development computer where CODESYS V3 is running.

  • “ CODESYS V3”

    The devices exist in the same network. The V3 runtime on the remote PLC provides a communication interface.

  • “ CODESYS V3 (via gateway)”

    The devices do not exist in the same network. They are connected via a V3 gateway.